| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.3.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.3.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_3_1_Manage_Information_Exchange_with_Patient_PHR |
| Title | AS.3.1 Manage Information Exchange with Patient PHR (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Support the ability to capture, and/or have interactions with patient PHR systems to enable the creation and maintenance of demographic, clinical and administrative information. |
| Purpose | The patient's PHR demographic, clinical and administrative data set is needed to support identification and to enhance the prospect for interoperability. The PHR Account Holder should be able to request or make changes to their demographic data and allow for export of all or parts of the demographic data to other systems. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Support the ability to capture, and/or have interactions with patient PHR systems to enable the creation and maintenance of demographic, clinical and administrative information.
The patient's PHR demographic, clinical and administrative data set is needed to support identification and to enhance the prospect for interoperability. The PHR Account Holder should be able to request or make changes to their demographic data and allow for export of all or parts of the demographic data to other systems.
| AS.3.1#01 | MAY |
The system MAY provide the ability to manage patient information (e.g., demographic, clinical and administrative) through an interaction with an external system (e.g., Personal Health Record). |
| AS.3.1#02 | MAY |
The system MAY transmit an alert or notification to a patient's provider that new information is available as a result of interaction with an external system (e.g., Personal Health Record system). |
| AS.3.1#03 | SHOULD |
The system SHOULD provide the ability to receive requests for patient information from external systems (e.g., patient's Personal Health Record). |
| AS.3.1#04 | SHOULD |
The system SHOULD provide the ability to transmit patient's information to an external system(e.g., patient's Personal Health Record). |
| AS.3.1#05 | SHOULD |
The system SHOULD transmit the status (e.g., acknowledgement, pending, rejected) of an external system's request for information. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.3.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support the ability to capture, and/or have interactions with patient PHR systems to enable the creation and maintenance of demographic, clinical and administrative information.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The patient's PHR demographic, clinical and administrative data set is needed to support identification and to enhance the prospect for interoperability. The PHR Account Holder should be able to request or make changes to their demographic data and allow for export of all or parts of the demographic data to other systems.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.3.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage patient information (e.g., demographic, clinical and administrative) through an interaction with an external system (e.g., Personal Health Record).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.3.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY transmit an alert or notification to a patient's provider that new information is available as a result of interaction with an external system (e.g., Personal Health Record system).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.3.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive requests for patient information from external systems (e.g., patient's Personal Health Record).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.3.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to transmit patient's information to an external system(e.g., patient's Personal Health Record).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.3.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD transmit the status (e.g., acknowledgement, pending, rejected) of an external system's request for information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.3.1",
"version" : "2.1.0",
"name" : "AS_3_1_Manage_Information_Exchange_with_Patient_PHR",
"title" : "AS.3.1 Manage Information Exchange with Patient PHR (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support the ability to capture, and/or have interactions with patient PHR systems to enable the creation and maintenance of demographic, clinical and administrative information.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "The patient's PHR demographic, clinical and administrative data set is needed to support identification and to enhance the prospect for interoperability. The PHR Account Holder should be able to request or make changes to their demographic data and allow for export of all or parts of the demographic data to other systems.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.3.1-01",
"label" : "AS.3.1#01",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage patient information (e.g., demographic, clinical and administrative) through an interaction with an external system (e.g., Personal Health Record)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.3.1-02",
"label" : "AS.3.1#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY transmit an alert or notification to a patient's provider that new information is available as a result of interaction with an external system (e.g., Personal Health Record system)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.3.1-03",
"label" : "AS.3.1#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive requests for patient information from external systems (e.g., patient's Personal Health Record)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.3.1-04",
"label" : "AS.3.1#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit patient's information to an external system(e.g., patient's Personal Health Record)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.3.1-05",
"label" : "AS.3.1#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD transmit the status (e.g., acknowledgement, pending, rejected) of an external system's request for information."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.